Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0496

reference: 235-tree-1
name: 0496
tree-preservation-order: undefined
235-tpo-1
uprn
address-text
point: POINT (-1.009442 50.851173)
geometry: MULTIPOLYGON (((-1.009385 50.851167,-1.009388 50.851178,-1.009396 50.851188,-1.009408 50.851196,-1.009424 50.851202,-1.009441 50.851204,-1.009459 50.851202,-1.009475 50.851197,-1.009487 50.851189,-1.009496 50.851179,-1.009499 50.851168,-1.009496 50.851157,-1.009488 50.851147,-1.009476 50.851139,-1.009460 50.851134,-1.009443 50.851132,-1.009425 50.851133,-1.009409 50.851138,-1.009396 50.851146,-1.009388 50.851156,-1.009385 50.851167)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL